Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e16e94a696df8385a55749a535a4fd4b7053811845f9cfa98b5c31e4ae7be579

Tx prefix hash: 0d51c56a3b691cb0300d2397eddf3b642a3be93c40e7e5d10f04a83be11e7caf
Tx public key: 6c827a69b633f4692bb829e3787a8264c1a0dc06c1adc7f1720732f8630301f0
Timestamp: 1584918461 Timestamp [UCT]: 2020-03-22 23:07:41 Age [y:d:h:m:s]: 04:241:00:13:33
Block: 86722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1069289 RingCT/type: yes/0
Extra: 016c827a69b633f4692bb829e3787a8264c1a0dc06c1adc7f1720732f8630301f002110000000e8a2ee0d9000000000000000000

1 output(s) for total of 316.704908266000 dcy

stealth address amount amount idx
00: d1375c5c9bb70e3abd9af434c4c58ef2b2e32b26eadcf5925cc4b231765158ec 316.704908266000 156502 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": 86732, "vin": [ { "gen": { "height": 86722 } } ], "vout": [ { "amount": 316704908266, "target": { "key": "d1375c5c9bb70e3abd9af434c4c58ef2b2e32b26eadcf5925cc4b231765158ec" } } ], "extra": [ 1, 108, 130, 122, 105, 182, 51, 244, 105, 43, 184, 41, 227, 120, 122, 130, 100, 193, 160, 220, 6, 193, 173, 199, 241, 114, 7, 50, 248, 99, 3, 1, 240, 2, 17, 0, 0, 0, 14, 138, 46, 224, 217, 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