Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5b1e371e597133642efd287c40e0e2476dcad90979cc8f07f610fb24fcb95d1

Tx prefix hash: 0df10cd971add12c4d314f2af2694282de7a58cd984df6798ec405c9181425fe
Tx public key: 847a615c2ff70a7ea3ce426a56735208637c4b605ae23e17c02590cc6ebe8015
Timestamp: 1634602323 Timestamp [UCT]: 2021-10-19 00:12:03 Age [y:d:h:m:s]: 03:147:15:33:34
Block: 355835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 883389 RingCT/type: yes/0
Extra: 01847a615c2ff70a7ea3ce426a56735208637c4b605ae23e17c02590cc6ebe80150211000000098d0de867000000000000000000

1 output(s) for total of 40.641651353000 dcy

stealth address amount amount idx
00: 6c641e671a3fad8dda09ae682ddbbbb8cb526c77f9e97275d23861d83ad352e4 40.641651353000 726283 of 0

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": 355845, "vin": [ { "gen": { "height": 355835 } } ], "vout": [ { "amount": 40641651353, "target": { "key": "6c641e671a3fad8dda09ae682ddbbbb8cb526c77f9e97275d23861d83ad352e4" } } ], "extra": [ 1, 132, 122, 97, 92, 47, 247, 10, 126, 163, 206, 66, 106, 86, 115, 82, 8, 99, 124, 75, 96, 90, 226, 62, 23, 192, 37, 144, 204, 110, 190, 128, 21, 2, 17, 0, 0, 0, 9, 141, 13, 232, 103, 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