Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 643cc129723b5137f4cf5403cafa99ba477aaaf3afbd4a199cabd04ce6b19fb1

Tx prefix hash: 764c1dff0d911e9d2e769f3e752b6b316d3029dfb58ee172f57a4a0fdf7976cf
Tx public key: c8021e95099720ddc3d578fb4b0c32f70e31e0e59c44ecaa7fa3a01e1f161b6b
Timestamp: 1577798493 Timestamp [UCT]: 2019-12-31 13:21:33 Age [y:d:h:m:s]: 05:064:07:18:02
Block: 35771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1195705 RingCT/type: yes/0
Extra: 01c8021e95099720ddc3d578fb4b0c32f70e31e0e59c44ecaa7fa3a01e1f161b6b0211000000078a2ee0d9000000000000000000

1 output(s) for total of 467.171866806000 dcy

stealth address amount amount idx
00: d33e887e54e94f509172e8ad990071115aa51df8a5c401d113ae898843ae57fd 467.171866806000 60399 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": 35781, "vin": [ { "gen": { "height": 35771 } } ], "vout": [ { "amount": 467171866806, "target": { "key": "d33e887e54e94f509172e8ad990071115aa51df8a5c401d113ae898843ae57fd" } } ], "extra": [ 1, 200, 2, 30, 149, 9, 151, 32, 221, 195, 213, 120, 251, 75, 12, 50, 247, 14, 49, 224, 229, 156, 68, 236, 170, 127, 163, 160, 30, 31, 22, 27, 107, 2, 17, 0, 0, 0, 7, 138, 46, 224, 217, 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