Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c69eb88785a5bd2de160ab021b7f47f87a61fab7c97ef56cb0b38db7e3d1377

Tx prefix hash: 809f2efa76c2c0a85225b20318c5289fa81edb76c23116c7a001489ef50da728
Tx public key: 8bba0d87e8e57ec03b1bdc3a9bd18a0a83c68fbb34441d15622bb59d3dc9bece
Timestamp: 1609076896 Timestamp [UCT]: 2020-12-27 13:48:16 Age [y:d:h:m:s]: 03:327:02:00:09
Block: 170374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 986105 RingCT/type: yes/0
Extra: 018bba0d87e8e57ec03b1bdc3a9bd18a0a83c68fbb34441d15622bb59d3dc9bece0211000001eaaad74b3a000000000000000000

1 output(s) for total of 167.294197365000 dcy

stealth address amount amount idx
00: 55c468ff82b1460b2183e50751c49d36fe474ccfed648275df95502e6c84356d 167.294197365000 319405 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": 170384, "vin": [ { "gen": { "height": 170374 } } ], "vout": [ { "amount": 167294197365, "target": { "key": "55c468ff82b1460b2183e50751c49d36fe474ccfed648275df95502e6c84356d" } } ], "extra": [ 1, 139, 186, 13, 135, 232, 229, 126, 192, 59, 27, 220, 58, 155, 209, 138, 10, 131, 198, 143, 187, 52, 68, 29, 21, 98, 43, 181, 157, 61, 201, 190, 206, 2, 17, 0, 0, 1, 234, 170, 215, 75, 58, 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