Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16f6f83d79623cde83fc2e7996a6f6f95230386f376d9558a184f27c1fa635f0

Tx prefix hash: 777caa7033ecab2d19635826fcb790aa576e95857ecacb61c3a44a67a9327c15
Tx public key: b387f323ee1fb4d9004ac6a7a733aab3e9d12c49439168c9daf6b39af962252c
Timestamp: 1737483470 Timestamp [UCT]: 2025-01-21 18:17:50 Age [y:d:h:m:s]: 00:335:08:02:48
Block: 1202301 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237267 RingCT/type: yes/0
Extra: 01b387f323ee1fb4d9004ac6a7a733aab3e9d12c49439168c9daf6b39af962252c02110000000e007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72359d27717c72eb44a3b2abb1f873cc0fd528922af9402accfd78dfcb4473cb 0.600000000000 1688964 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": 1202311, "vin": [ { "gen": { "height": 1202301 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72359d27717c72eb44a3b2abb1f873cc0fd528922af9402accfd78dfcb4473cb" } } ], "extra": [ 1, 179, 135, 243, 35, 238, 31, 180, 217, 0, 74, 198, 167, 167, 51, 170, 179, 233, 209, 44, 73, 67, 145, 104, 201, 218, 246, 179, 154, 249, 98, 37, 44, 2, 17, 0, 0, 0, 14, 0, 127, 151, 138, 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