Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00fa739c2cbd9b8bf78f3a6e9c4fb73b145bf6610474e7b2870ee485ecdf0654

Tx prefix hash: 9e2432b6c69998711219efce9e16d95723eba54ef2153d3851afc2cff9d04a6c
Tx public key: ab80d720c189605edcc8ae207ea71616276af653e3bb8e7c71cd3095a46ca7e4
Timestamp: 1699593807 Timestamp [UCT]: 2023-11-10 05:23:27 Age [y:d:h:m:s]: 01:148:15:16:29
Block: 888387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367398 RingCT/type: yes/0
Extra: 01ab80d720c189605edcc8ae207ea71616276af653e3bb8e7c71cd3095a46ca7e40211000000024b8f5122000000000000000000

1 output(s) for total of 0.698883975000 dcy

stealth address amount amount idx
00: 16229b47a2308da940d6697494fa1ae416b85272df93025b3ae44804f885179a 0.698883975000 1344326 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": 888397, "vin": [ { "gen": { "height": 888387 } } ], "vout": [ { "amount": 698883975, "target": { "key": "16229b47a2308da940d6697494fa1ae416b85272df93025b3ae44804f885179a" } } ], "extra": [ 1, 171, 128, 215, 32, 193, 137, 96, 94, 220, 200, 174, 32, 126, 167, 22, 22, 39, 106, 246, 83, 227, 187, 142, 124, 113, 205, 48, 149, 164, 108, 167, 228, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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