Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff6359af8988672c4004bba5797111b732c64a4a04ed53d86782653142d6c528

Tx prefix hash: cc5f4895e414835b5a0cce7f32bf6517a87266a63baa565d28d8be6378ef43e8
Tx public key: cb7748cfe9949b8a7356dcc79c8c8acb6f297dbd33eaab3c36df02ae5b6c4624
Timestamp: 1710530699 Timestamp [UCT]: 2024-03-15 19:24:59 Age [y:d:h:m:s]: 01:033:22:38:50
Block: 979064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285244 RingCT/type: yes/0
Extra: 01cb7748cfe9949b8a7356dcc79c8c8acb6f297dbd33eaab3c36df02ae5b6c462402110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 804ba16f7c5345e2228bb10095d729e253076e1a63dc73c93fc385e580dd71d7 0.600000000000 1439095 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": 979074, "vin": [ { "gen": { "height": 979064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "804ba16f7c5345e2228bb10095d729e253076e1a63dc73c93fc385e580dd71d7" } } ], "extra": [ 1, 203, 119, 72, 207, 233, 148, 155, 138, 115, 86, 220, 199, 156, 140, 138, 203, 111, 41, 125, 189, 51, 234, 171, 60, 54, 223, 2, 174, 91, 108, 70, 36, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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