Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 772c7dc1a06598c10d8dca441deac6d4969f4d3f4bd32e2adbd16af03ea0e305

Tx prefix hash: 28e0602b6bffbd4e7c271b43f406abac5904731a7780a0c008fc1f70352f71f5
Tx public key: 5ee0ae7e46a5b6e55d0789e5e282b218971244c495f43216b0f2f8af97bb4405
Timestamp: 1593276338 Timestamp [UCT]: 2020-06-27 16:45:38 Age [y:d:h:m:s]: 04:142:08:32:53
Block: 111322 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1043318 RingCT/type: yes/0
Extra: 015ee0ae7e46a5b6e55d0789e5e282b218971244c495f43216b0f2f8af97bb440502110000001e46a11e8a000000000000000000

1 output(s) for total of 262.509332786000 dcy

stealth address amount amount idx
00: 6904492e4efdfc0a1a084bdb657809c66b37d0b44ee1292435ae6a6ec45c4aaa 262.509332786000 192417 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": 111332, "vin": [ { "gen": { "height": 111322 } } ], "vout": [ { "amount": 262509332786, "target": { "key": "6904492e4efdfc0a1a084bdb657809c66b37d0b44ee1292435ae6a6ec45c4aaa" } } ], "extra": [ 1, 94, 224, 174, 126, 70, 165, 182, 229, 93, 7, 137, 229, 226, 130, 178, 24, 151, 18, 68, 196, 149, 244, 50, 22, 176, 242, 248, 175, 151, 187, 68, 5, 2, 17, 0, 0, 0, 30, 70, 161, 30, 138, 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