Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf28538e3f8860de70bfbf59d8f7a06efb2f46d50e28e011f64f6760fcc8d0dd

Tx prefix hash: 3b79eb1ce93dc3f3179d1d6f52bea18fd379895c66af58d485bbe0c435514f2d
Tx public key: 31e1f80d07e3c8391b2179a8657e6dbfb9961ed30f0c669e99ad3c78b26c9dae
Timestamp: 1764362658 Timestamp [UCT]: 2025-11-28 20:44:18 Age [y:d:h:m:s]: 00:031:14:19:58
Block: 1422217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22619 RingCT/type: yes/0
Extra: 0131e1f80d07e3c8391b2179a8657e6dbfb9961ed30f0c669e99ad3c78b26c9dae02110000000370609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33b0c7d919149333331798ce155e389e8f9e5552772fa8594f339a3b7ed95979 0.600000000000 1910782 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": 1422227, "vin": [ { "gen": { "height": 1422217 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33b0c7d919149333331798ce155e389e8f9e5552772fa8594f339a3b7ed95979" } } ], "extra": [ 1, 49, 225, 248, 13, 7, 227, 200, 57, 27, 33, 121, 168, 101, 126, 109, 191, 185, 150, 30, 211, 15, 12, 102, 158, 153, 173, 60, 120, 178, 108, 157, 174, 2, 17, 0, 0, 0, 3, 112, 96, 157, 3, 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