Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3f1de53ade1d24459c737346cc162846e06a3d271a8e8fa11bb7367b38e3804

Tx prefix hash: 32dc061df5119102de1bae9da3266df9577cc44f54c78311208090579fb9aaf2
Tx public key: 4c6157959d3e11eeb916f59bfe67a203e16ca18f9e1e739bfd6714fef2da091b
Timestamp: 1727128886 Timestamp [UCT]: 2024-09-23 22:01:26 Age [y:d:h:m:s]: 01:041:02:07:30
Block: 1116663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287744 RingCT/type: yes/0
Extra: 014c6157959d3e11eeb916f59bfe67a203e16ca18f9e1e739bfd6714fef2da091b021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ae3398dd72bfa2f4ec80a7eab8c437f9a44b0c8564768ada8885fa5d461e6f4 0.600000000000 1597224 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": 1116673, "vin": [ { "gen": { "height": 1116663 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ae3398dd72bfa2f4ec80a7eab8c437f9a44b0c8564768ada8885fa5d461e6f4" } } ], "extra": [ 1, 76, 97, 87, 149, 157, 62, 17, 238, 185, 22, 245, 155, 254, 103, 162, 3, 225, 108, 161, 143, 158, 30, 115, 155, 253, 103, 20, 254, 242, 218, 9, 27, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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