Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 555a1d0bfccfbd103d0662d7d213478007e65b35149c519d0b89047320bef091

Tx prefix hash: 5b94a4e4ddc1e4e08530a7522f7d6240ea6cfdeebd747e2c7513628b13a2c7fa
Tx public key: 40459d50bb6832fc2cabe934c7f42a1a0e692f1640126994d1c3793e90535c11
Timestamp: 1749546961 Timestamp [UCT]: 2025-06-10 09:16:01 Age [y:d:h:m:s]: 00:162:04:58:50
Block: 1301970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113601 RingCT/type: yes/0
Extra: 0140459d50bb6832fc2cabe934c7f42a1a0e692f1640126994d1c3793e90535c11021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a44cdb04fabbf8f61526231e4e300350de343fc5bb6a2e71f945d0b0477a87b8 0.600000000000 1789537 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": 1301980, "vin": [ { "gen": { "height": 1301970 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a44cdb04fabbf8f61526231e4e300350de343fc5bb6a2e71f945d0b0477a87b8" } } ], "extra": [ 1, 64, 69, 157, 80, 187, 104, 50, 252, 44, 171, 233, 52, 199, 244, 42, 26, 14, 105, 47, 22, 64, 18, 105, 148, 209, 195, 121, 62, 144, 83, 92, 17, 2, 17, 0, 0, 0, 2, 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