Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d44b57f2f2d2e4645cd6ad246c3ba0292d3c3f6ce7ff151422eca06da8fa5e5a

Tx prefix hash: 36b1e49338997be5c460296ddcf53f5a87968661465a27b981295b805bfe942e
Tx public key: 4c763f8cc13ba0b3f4e3e5c038e2c1feb9e47f1a3f72422532b7005764b0ded8
Timestamp: 1742739909 Timestamp [UCT]: 2025-03-23 14:25:09 Age [y:d:h:m:s]: 00:280:04:20:25
Block: 1245610 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198031 RingCT/type: yes/0
Extra: 014c763f8cc13ba0b3f4e3e5c038e2c1feb9e47f1a3f72422532b7005764b0ded802110000000624ff4ea1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bcac4cd59cbab42ff0cd522d76c23095254e0d4f9e401324b9ab2110c7ab2de4 0.600000000000 1732601 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": 1245620, "vin": [ { "gen": { "height": 1245610 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcac4cd59cbab42ff0cd522d76c23095254e0d4f9e401324b9ab2110c7ab2de4" } } ], "extra": [ 1, 76, 118, 63, 140, 193, 59, 160, 179, 244, 227, 229, 192, 56, 226, 193, 254, 185, 228, 127, 26, 63, 114, 66, 37, 50, 183, 0, 87, 100, 176, 222, 216, 2, 17, 0, 0, 0, 6, 36, 255, 78, 161, 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