Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23800198dd00c27e88c15392e47a7e2fb4612712d19b314497a6bed4b86df63f

Tx prefix hash: 38c89af5fd69dcf758a19ae6c710d2f2df0d2ff16c801853f843c9d35c91db0f
Tx public key: 84a6a20b397408286c3db5f9278d2dcfb371751dfb8a0ebde4275ef3db0a88c4
Timestamp: 1712634449 Timestamp [UCT]: 2024-04-09 03:47:29 Age [y:d:h:m:s]: 00:233:16:46:32
Block: 996469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167327 RingCT/type: yes/0
Extra: 0184a6a20b397408286c3db5f9278d2dcfb371751dfb8a0ebde4275ef3db0a88c40211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52b543c5c2ffd584a040106b6dc0a1ca50fafd4ec545699aaea7ff5200396dbe 0.600000000000 1456887 of 15

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": 996479, "vin": [ { "gen": { "height": 996469 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52b543c5c2ffd584a040106b6dc0a1ca50fafd4ec545699aaea7ff5200396dbe" } } ], "extra": [ 1, 132, 166, 162, 11, 57, 116, 8, 40, 108, 61, 181, 249, 39, 141, 45, 207, 179, 113, 117, 29, 251, 138, 14, 189, 228, 39, 94, 243, 219, 10, 136, 196, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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