Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab27af84c1f53cc2f5c24cbe70d5e39942c1f1b9db5821fdf3eda04e101f4eac

Tx prefix hash: 28ff4ac24f93054c510760813ee0b9f4316d6f29c72912b223b63eba906eaa35
Tx public key: 0a726c00c06c6580e819ddc0799d611f31f37d3d411bb2eb5e193d2a8bf3d1d1
Timestamp: 1750868290 Timestamp [UCT]: 2025-06-25 16:18:10 Age [y:d:h:m:s]: 00:148:21:34:45
Block: 1312631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104357 RingCT/type: yes/0
Extra: 010a726c00c06c6580e819ddc0799d611f31f37d3d411bb2eb5e193d2a8bf3d1d1021100000003e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2b5c930af6544f361aff8448b2f24ee07b8c2bc6be01767229ace9b95345ed4 0.600000000000 1800264 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": 1312641, "vin": [ { "gen": { "height": 1312631 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2b5c930af6544f361aff8448b2f24ee07b8c2bc6be01767229ace9b95345ed4" } } ], "extra": [ 1, 10, 114, 108, 0, 192, 108, 101, 128, 232, 25, 221, 192, 121, 157, 97, 31, 49, 243, 125, 61, 65, 27, 178, 235, 94, 25, 61, 42, 139, 243, 209, 209, 2, 17, 0, 0, 0, 3, 228, 220, 144, 9, 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