Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 341edf83e2b704856297faf8e622c6a3c9ddeb856ffb9c1bc45c8c4bf4bd079d

Tx prefix hash: 4bbf4f22a7be82848af0ee2c51a0849f116857bc247b2cdda461e4a534c12c94
Tx public key: a45d179f4dddc773cdf8ffd57f80c30326dc297c12ee2fbc76a81223031a4216
Timestamp: 1702922739 Timestamp [UCT]: 2023-12-18 18:05:39 Age [y:d:h:m:s]: 01:142:19:02:49
Block: 915976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363202 RingCT/type: yes/0
Extra: 01a45d179f4dddc773cdf8ffd57f80c30326dc297c12ee2fbc76a81223031a421602110000000575e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32e4449e988452b4909aea8caaf02d21ec407f33c725f64a4dc8391262f778b8 0.600000000000 1373410 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": 915986, "vin": [ { "gen": { "height": 915976 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32e4449e988452b4909aea8caaf02d21ec407f33c725f64a4dc8391262f778b8" } } ], "extra": [ 1, 164, 93, 23, 159, 77, 221, 199, 115, 205, 248, 255, 213, 127, 128, 195, 3, 38, 220, 41, 124, 18, 238, 47, 188, 118, 168, 18, 35, 3, 26, 66, 22, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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