Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f7d43d1119eb3195ed2fb03014bf98e8c71b26ad9a4a04746a46fea5b5ae036

Tx prefix hash: c507db5a9bec465d9bdfca6e69b4e70ef3c64c52a38b0470040cbfc57e6bfe4f
Tx public key: 9ed7ec7dc81fcd94ce5e46e252ca20f81781582f297fe247f2cc8448dd423191
Timestamp: 1707557060 Timestamp [UCT]: 2024-02-10 09:24:20 Age [y:d:h:m:s]: 01:272:06:40:20
Block: 954388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 453367 RingCT/type: yes/0
Extra: 019ed7ec7dc81fcd94ce5e46e252ca20f81781582f297fe247f2cc8448dd4231910211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 193279845defc8cd2ace038b9e3b51a5e5d37149e0f55a2525ec33deb5bf1e11 0.600000000000 1413668 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": 954398, "vin": [ { "gen": { "height": 954388 } } ], "vout": [ { "amount": 600000000, "target": { "key": "193279845defc8cd2ace038b9e3b51a5e5d37149e0f55a2525ec33deb5bf1e11" } } ], "extra": [ 1, 158, 215, 236, 125, 200, 31, 205, 148, 206, 94, 70, 226, 82, 202, 32, 248, 23, 129, 88, 47, 41, 127, 226, 71, 242, 204, 132, 72, 221, 66, 49, 145, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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