Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 206f1d588a2d2b6be2b325328618dbca5e892f2c47beb5e56425db330b8cbc81

Tx prefix hash: 8ae6b78a5c3d4f6395d87563dc6f58f41360e004621d85b5812cfc084bf96f9c
Tx public key: 0ccb7fe55849431399b27c7f7f7edd368d76b5448a7304200951898d87c83b71
Timestamp: 1580977209 Timestamp [UCT]: 2020-02-06 08:20:09 Age [y:d:h:m:s]: 05:027:23:32:50
Block: 59705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1172110 RingCT/type: yes/0
Extra: 010ccb7fe55849431399b27c7f7f7edd368d76b5448a7304200951898d87c83b71021133b1e09300000000000000000000000000

1 output(s) for total of 389.200481638000 dcy

stealth address amount amount idx
00: eea7da58feda0a5543c1d2440135f0e576049fa3ea81104c75e0876bcf056684 389.200481638000 110181 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": 59715, "vin": [ { "gen": { "height": 59705 } } ], "vout": [ { "amount": 389200481638, "target": { "key": "eea7da58feda0a5543c1d2440135f0e576049fa3ea81104c75e0876bcf056684" } } ], "extra": [ 1, 12, 203, 127, 229, 88, 73, 67, 19, 153, 178, 124, 127, 127, 126, 221, 54, 141, 118, 181, 68, 138, 115, 4, 32, 9, 81, 137, 141, 135, 200, 59, 113, 2, 17, 51, 177, 224, 147, 0, 0, 0, 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