Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b51b69ddb11b035d4958dfbf0745b83d65bd0d1c39dcce60cfa3301373f27b4d

Tx prefix hash: 7d35b04e9ce1ecc6e57e3dd30189f2cb8ad4edcb6f77802373149d0908eedde3
Tx public key: 2a9231e6cb6d06f0ba85f9070dd6ea6e340e901ee022ece6ad72aa2426677c63
Timestamp: 1706327553 Timestamp [UCT]: 2024-01-27 03:52:33 Age [y:d:h:m:s]: 02:004:03:56:01
Block: 944178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 522581 RingCT/type: yes/0
Extra: 012a9231e6cb6d06f0ba85f9070dd6ea6e340e901ee022ece6ad72aa2426677c630211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27016ecda0b771ddca6fb2f793013815c2bdb4d955c0eedfa6d4440d145edf2c 0.600000000000 1402412 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": 944188, "vin": [ { "gen": { "height": 944178 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27016ecda0b771ddca6fb2f793013815c2bdb4d955c0eedfa6d4440d145edf2c" } } ], "extra": [ 1, 42, 146, 49, 230, 203, 109, 6, 240, 186, 133, 249, 7, 13, 214, 234, 110, 52, 14, 144, 30, 224, 34, 236, 230, 173, 114, 170, 36, 38, 103, 124, 99, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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