Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36e5831fd2126148713d77b36cd275dbd32d08182b73331f5a57747cce25154f

Tx prefix hash: 6671743c46442daf3259af04df47325c2cc92fb9d7d99234d2a2b604d07a14de
Tx public key: 9c421f7d28d6de2657722d7ec04b780acf58881e1aef4cbf9c82823b728cd27f
Timestamp: 1721841259 Timestamp [UCT]: 2024-07-24 17:14:19 Age [y:d:h:m:s]: 00:316:14:48:46
Block: 1072812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226252 RingCT/type: yes/0
Extra: 019c421f7d28d6de2657722d7ec04b780acf58881e1aef4cbf9c82823b728cd27f021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9e5cc845164bdcbaf1b91c39d7d581ae2e390ca03bdbbc777b5d5339387b92d 0.600000000000 1545309 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": 1072822, "vin": [ { "gen": { "height": 1072812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9e5cc845164bdcbaf1b91c39d7d581ae2e390ca03bdbbc777b5d5339387b92d" } } ], "extra": [ 1, 156, 66, 31, 125, 40, 214, 222, 38, 87, 114, 45, 126, 192, 75, 120, 10, 207, 88, 136, 30, 26, 239, 76, 191, 156, 130, 130, 59, 114, 140, 210, 127, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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