Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbc577dddf33344460cf7c26fd46cf2582ea11e1ac9f8e663d12ac31c8012222

Tx prefix hash: d0e4f9d8a968b45ca9ae8c9bd6f60a867aa453710917dffaaa1eece8256510e6
Tx public key: 512ab86057b40f3bf96a7ff26b0a7cf3bdb46f47b007ad8312c577a00a748110
Timestamp: 1749732505 Timestamp [UCT]: 2025-06-12 12:48:25 Age [y:d:h:m:s]: 00:151:08:45:57
Block: 1303457 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105894 RingCT/type: yes/0
Extra: 01512ab86057b40f3bf96a7ff26b0a7cf3bdb46f47b007ad8312c577a00a748110021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56769a7fa664ec5bfdc4e366335a15434dc6e5404fac51476ae3f7ae3d257c38 0.600000000000 1791038 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": 1303467, "vin": [ { "gen": { "height": 1303457 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56769a7fa664ec5bfdc4e366335a15434dc6e5404fac51476ae3f7ae3d257c38" } } ], "extra": [ 1, 81, 42, 184, 96, 87, 180, 15, 59, 249, 106, 127, 242, 107, 10, 124, 243, 189, 180, 111, 71, 176, 7, 173, 131, 18, 197, 119, 160, 10, 116, 129, 16, 2, 17, 0, 0, 0, 1, 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