Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb1dd3501c3f829af7203398e0abee10c894d177334a413df0127585bcaee64a

Tx prefix hash: d80e6025ec97ea21f0050c9b46a5f904ae70bf554955e61c5d74801408db4cb2
Tx public key: 0df1eb8ad0f69b0e803d97bf159f6bffe1e382bea12cdb4dab0eeca0aedf4907
Timestamp: 1708671214 Timestamp [UCT]: 2024-02-23 06:53:34 Age [y:d:h:m:s]: 01:259:22:19:03
Block: 963633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 444508 RingCT/type: yes/0
Extra: 010df1eb8ad0f69b0e803d97bf159f6bffe1e382bea12cdb4dab0eeca0aedf490702110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71528a5284114a3d180d6129183b36d109c9ac563e412fc3a4dc23807f242676 0.600000000000 1423350 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": 963643, "vin": [ { "gen": { "height": 963633 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71528a5284114a3d180d6129183b36d109c9ac563e412fc3a4dc23807f242676" } } ], "extra": [ 1, 13, 241, 235, 138, 208, 246, 155, 14, 128, 61, 151, 191, 21, 159, 107, 255, 225, 227, 130, 190, 161, 44, 219, 77, 171, 14, 236, 160, 174, 223, 73, 7, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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