Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47ec588be282b6a41a87d837b3c49cad2d89221c9ff0941e1cbfb2c6b0fdc4f0

Tx prefix hash: 4fcd34ae2bd243d4c4d49e7ef667d917a3cf24e290671a24ea66580c963b8f70
Tx public key: 38302d7b86aaddf8690011bc9ef40a334c51e2304d7e21ef2edd001fad9da5b6
Timestamp: 1753009035 Timestamp [UCT]: 2025-07-20 10:57:15 Age [y:d:h:m:s]: 00:123:22:02:08
Block: 1329474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87359 RingCT/type: yes/0
Extra: 0138302d7b86aaddf8690011bc9ef40a334c51e2304d7e21ef2edd001fad9da5b602110000000843846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11ee0e9e773a9d6d232f29b002ca53909d2291ea43c1105371aaec0b96b647cf 0.600000000000 1817251 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": 1329484, "vin": [ { "gen": { "height": 1329474 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11ee0e9e773a9d6d232f29b002ca53909d2291ea43c1105371aaec0b96b647cf" } } ], "extra": [ 1, 56, 48, 45, 123, 134, 170, 221, 248, 105, 0, 17, 188, 158, 244, 10, 51, 76, 81, 226, 48, 77, 126, 33, 239, 46, 221, 0, 31, 173, 157, 165, 182, 2, 17, 0, 0, 0, 8, 67, 132, 109, 102, 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