Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa1bc1022ab6444e9210dd557e75e2f250f1d027b9cf42ef34a2f905228c367d

Tx prefix hash: 0a78fd441eea3446f3f53053ea62abe2a2d529dd80de174e3cf8811b15192e55
Tx public key: 84c94d3e47384df3bbe39ef05304d95be1f87603b425e53b5f0901c4d114f0e7
Timestamp: 1576341130 Timestamp [UCT]: 2019-12-14 16:32:10 Age [y:d:h:m:s]: 05:032:08:31:13
Block: 27112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1169716 RingCT/type: yes/0
Extra: 0184c94d3e47384df3bbe39ef05304d95be1f87603b425e53b5f0901c4d114f0e702110000003e9159db1e000000000000000000

1 output(s) for total of 499.109099949000 dcy

stealth address amount amount idx
00: 0c971d7c0cf111c60e8f93d2d181fb2d62a65bcb360f737b8d8b7b22ada824f7 499.109099949000 44852 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": 27122, "vin": [ { "gen": { "height": 27112 } } ], "vout": [ { "amount": 499109099949, "target": { "key": "0c971d7c0cf111c60e8f93d2d181fb2d62a65bcb360f737b8d8b7b22ada824f7" } } ], "extra": [ 1, 132, 201, 77, 62, 71, 56, 77, 243, 187, 227, 158, 240, 83, 4, 217, 91, 225, 248, 118, 3, 180, 37, 229, 59, 95, 9, 1, 196, 209, 20, 240, 231, 2, 17, 0, 0, 0, 62, 145, 89, 219, 30, 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