Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a69123344dfe2ccaab6dbeae0ee987dda8d20ac417cfaaff87b5440223f98bb

Tx prefix hash: 607b01a0d4c30b47986a0721e9bcc42fdd593a2e81f785a61ee3158fb91fb0c5
Tx public key: cb53ffa35e93da03d681480834f67e724c5772cf7a4dbded6f4e1bfc07825a8c
Timestamp: 1703908678 Timestamp [UCT]: 2023-12-30 03:57:58 Age [y:d:h:m:s]: 01:099:03:19:48
Block: 924146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331962 RingCT/type: yes/0
Extra: 01cb53ffa35e93da03d681480834f67e724c5772cf7a4dbded6f4e1bfc07825a8c0211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e094c753f5f0f00d494dcec1ebf37df8e219d8f75b08c422799d86cecf7c3769 0.600000000000 1381890 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": 924156, "vin": [ { "gen": { "height": 924146 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e094c753f5f0f00d494dcec1ebf37df8e219d8f75b08c422799d86cecf7c3769" } } ], "extra": [ 1, 203, 83, 255, 163, 94, 147, 218, 3, 214, 129, 72, 8, 52, 246, 126, 114, 76, 87, 114, 207, 122, 77, 189, 237, 111, 78, 27, 252, 7, 130, 90, 140, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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