Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df31317375c55aee68a23c31ab131217f7ea0f009c933fecdf75c030e7c87c81

Tx prefix hash: 8be5c1c165948c56bc96ff9fcaf7fc905a1551ed280875fe00ccb6000c6c09b0
Tx public key: d7b7777337e4bec3d1816bfa8ca1532c15ea62abff6840cc86cfcfa333e5d3e3
Timestamp: 1657147575 Timestamp [UCT]: 2022-07-06 22:46:15 Age [y:d:h:m:s]: 02:178:00:19:43
Block: 538175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 648579 RingCT/type: yes/0
Extra: 01d7b7777337e4bec3d1816bfa8ca1532c15ea62abff6840cc86cfcfa333e5d3e302110000001a4da16a3a000000000000000000

1 output(s) for total of 10.111206209000 dcy

stealth address amount amount idx
00: b9c0ec3d80c5b893c35841b778e5bb944b989ca37875485b0b0e6583210cae46 10.111206209000 968142 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": 538185, "vin": [ { "gen": { "height": 538175 } } ], "vout": [ { "amount": 10111206209, "target": { "key": "b9c0ec3d80c5b893c35841b778e5bb944b989ca37875485b0b0e6583210cae46" } } ], "extra": [ 1, 215, 183, 119, 115, 55, 228, 190, 195, 209, 129, 107, 250, 140, 161, 83, 44, 21, 234, 98, 171, 255, 104, 64, 204, 134, 207, 207, 163, 51, 229, 211, 227, 2, 17, 0, 0, 0, 26, 77, 161, 106, 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