Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce3e28e20ca1df09b47822b4ee621126a15c82f5b00d102a0e9406f7bd4e73df

Tx prefix hash: ca22ed0eb042c7c37792572cafa861e81273583cbc788e0bd7bf6361fa4c1055
Tx public key: dba91be08d0c8527fdc365ec7d099e5c7fd69ad5109b3b51f380824c00fa393d
Timestamp: 1583750441 Timestamp [UCT]: 2020-03-09 10:40:41 Age [y:d:h:m:s]: 05:240:15:30:54
Block: 79084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1325390 RingCT/type: yes/0
Extra: 01dba91be08d0c8527fdc365ec7d099e5c7fd69ad5109b3b51f380824c00fa393d02110000000a6d997e00000000000000000000

1 output(s) for total of 335.733056956000 dcy

stealth address amount amount idx
00: 5b1fdceca7ab8556321089f6651b261b672cf3d8066faa771d2020f2a6c70e6a 335.733056956000 144816 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": 79094, "vin": [ { "gen": { "height": 79084 } } ], "vout": [ { "amount": 335733056956, "target": { "key": "5b1fdceca7ab8556321089f6651b261b672cf3d8066faa771d2020f2a6c70e6a" } } ], "extra": [ 1, 219, 169, 27, 224, 141, 12, 133, 39, 253, 195, 101, 236, 125, 9, 158, 92, 127, 214, 154, 213, 16, 155, 59, 81, 243, 128, 130, 76, 0, 250, 57, 61, 2, 17, 0, 0, 0, 10, 109, 153, 126, 0, 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