Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc0f88db17d2bbb160a1907b33417b984a279b0c5ed68605a3e14931a52eb89c

Tx prefix hash: c5a7d8a599f6cb1545f4364e74009eaf638c0f83c04ad6744c417e90b00b4461
Tx public key: a6bfc4b7fd7f6321df1b4cdfa316255d304a69acc01ec8a9709ded6395055307
Timestamp: 1724010790 Timestamp [UCT]: 2024-08-18 19:53:10 Age [y:d:h:m:s]: 01:081:04:12:10
Block: 1090815 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316466 RingCT/type: yes/0
Extra: 01a6bfc4b7fd7f6321df1b4cdfa316255d304a69acc01ec8a9709ded639505530702110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f764c52ea162b079361722af0ebd9d5cd09f0711fea62f624657c37ddd3134d1 0.600000000000 1565440 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": 1090825, "vin": [ { "gen": { "height": 1090815 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f764c52ea162b079361722af0ebd9d5cd09f0711fea62f624657c37ddd3134d1" } } ], "extra": [ 1, 166, 191, 196, 183, 253, 127, 99, 33, 223, 27, 76, 223, 163, 22, 37, 93, 48, 74, 105, 172, 192, 30, 200, 169, 112, 157, 237, 99, 149, 5, 83, 7, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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