Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: b62ac3ec48ed72aa0537dcfe6a853c65c46ed8213afc3f9b587031ade2fa0547

Tx prefix hash: 574c029e83ba98e99c7007e663b409a92df6bbcf4d9662bd766008d73d7253a4
Tx public key: 1310032e7dd2ffec756f1cc600bc01e7f40ed6db082b46d1ec67a0456e5331d1
Timestamp: 1750921621 Timestamp [UCT]: 2025-06-26 07:07:01 Age [y:d:h:m:s]: 00:144:06:08:38
Block: 1313026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101088 RingCT/type: yes/0
Extra: 011310032e7dd2ffec756f1cc600bc01e7f40ed6db082b46d1ec67a0456e5331d10211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 423b80d7992a3bf0d9e5f75c4dc7e417b47c836c10b0cb2b8402c087abcf9f04 0.600000000000 1800663 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1313036, "vin": [ { "gen": { "height": 1313026 } } ], "vout": [ { "amount": 600000000, "target": { "key": "423b80d7992a3bf0d9e5f75c4dc7e417b47c836c10b0cb2b8402c087abcf9f04" } } ], "extra": [ 1, 19, 16, 3, 46, 125, 210, 255, 236, 117, 111, 28, 198, 0, 188, 1, 231, 244, 14, 214, 219, 8, 43, 70, 209, 236, 103, 160, 69, 110, 83, 49, 209, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8