Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19b9e455c0ca3c4d4feb462f98e416e68ed2a18163c997515b640d9944fc9144

Tx prefix hash: ea7f830a54ff96ce29f9b1261ea1507556df1c771788995e4e38f08f184cc7e9
Tx public key: 1b0acc6b09c6608ec50eb8e693fc1bd09801e46814ee640fd94b635f29c1853e
Timestamp: 1743746041 Timestamp [UCT]: 2025-04-04 05:54:01 Age [y:d:h:m:s]: 00:005:06:00:02
Block: 1253927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3761 RingCT/type: yes/0
Extra: 011b0acc6b09c6608ec50eb8e693fc1bd09801e46814ee640fd94b635f29c1853e0211000000034060f6d2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fbdbf4611c38c6be5b493f6accfba9a5c31a2c1dea812183b95b26b7f1785ba7 0.600000000000 1741008 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": 1253937, "vin": [ { "gen": { "height": 1253927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fbdbf4611c38c6be5b493f6accfba9a5c31a2c1dea812183b95b26b7f1785ba7" } } ], "extra": [ 1, 27, 10, 204, 107, 9, 198, 96, 142, 197, 14, 184, 230, 147, 252, 27, 208, 152, 1, 228, 104, 20, 238, 100, 15, 217, 75, 99, 95, 41, 193, 133, 62, 2, 17, 0, 0, 0, 3, 64, 96, 246, 210, 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