Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23460c4e8cb72207f19c0c2c6ddd4ba6e1a26e18364d929b602e88588f49da5c

Tx prefix hash: 6e042104473b4fe09276d434509021dd1bcf4f8756c9897feb2b8862efa11f37
Tx public key: bde9766432667d6c7e92be5bfdfa17a2e173830263a639b60fcc64b5d7910df4
Timestamp: 1714909131 Timestamp [UCT]: 2024-05-05 11:38:51 Age [y:d:h:m:s]: 00:287:04:37:03
Block: 1015361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205229 RingCT/type: yes/0
Extra: 01bde9766432667d6c7e92be5bfdfa17a2e173830263a639b60fcc64b5d7910df402110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7a61bb629816a5c385b543191ef5ad1c3fa7215c55c587c61a8b6d6d537d54c 0.600000000000 1478702 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": 1015371, "vin": [ { "gen": { "height": 1015361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7a61bb629816a5c385b543191ef5ad1c3fa7215c55c587c61a8b6d6d537d54c" } } ], "extra": [ 1, 189, 233, 118, 100, 50, 102, 125, 108, 126, 146, 190, 91, 253, 250, 23, 162, 225, 115, 131, 2, 99, 166, 57, 182, 15, 204, 100, 181, 215, 145, 13, 244, 2, 17, 0, 0, 0, 4, 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