Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c6aafcd30412361456b917f6ee5185e3c43394b2397f6565ae2c6fa52aa2f18

Tx prefix hash: a9e2180f5e6d3eebb7f261b62cafe95cdc86791c87746adc758d7f6fd0404575
Tx public key: 6fe93ae1718f505d500d5ba79ab389e43c914b5b1bbf83cb591cd7d14c19c356
Timestamp: 1681836977 Timestamp [UCT]: 2023-04-18 16:56:17 Age [y:d:h:m:s]: 02:204:02:36:09
Block: 741407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 665734 RingCT/type: yes/0
Extra: 016fe93ae1718f505d500d5ba79ab389e43c914b5b1bbf83cb591cd7d14c19c3560211000000015029cbac000000000000000000

1 output(s) for total of 2.144919769000 dcy

stealth address amount amount idx
00: e9bc6f49a30bbe0e8d3deb9dcf91f9927d27a1286f5539c4990863cd5527b098 2.144919769000 1188336 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": 741417, "vin": [ { "gen": { "height": 741407 } } ], "vout": [ { "amount": 2144919769, "target": { "key": "e9bc6f49a30bbe0e8d3deb9dcf91f9927d27a1286f5539c4990863cd5527b098" } } ], "extra": [ 1, 111, 233, 58, 225, 113, 143, 80, 93, 80, 13, 91, 167, 154, 179, 137, 228, 60, 145, 75, 91, 27, 191, 131, 203, 89, 28, 215, 209, 76, 25, 195, 86, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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