Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0be9ef20300584c4a64ce3699a20094f2608ea423ee30f61ef2fd748295d31fd

Tx prefix hash: 10de58611df2ef4ba82042aa7f0664a043afb98691a8e2bc7cec2e06d3f5895e
Tx public key: 83b89edecd8155a7e9901db9491a938b18f8beb07d97c47cbded21ea843643e2
Timestamp: 1739895234 Timestamp [UCT]: 2025-02-18 16:13:54 Age [y:d:h:m:s]: 00:347:19:47:30
Block: 1222027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246282 RingCT/type: yes/0
Extra: 0183b89edecd8155a7e9901db9491a938b18f8beb07d97c47cbded21ea843643e20211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3af90d69c723fd7ab4eb63dc118da0ad50bc1e853e4c374542d39f726af54498 0.600000000000 1708874 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": 1222037, "vin": [ { "gen": { "height": 1222027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3af90d69c723fd7ab4eb63dc118da0ad50bc1e853e4c374542d39f726af54498" } } ], "extra": [ 1, 131, 184, 158, 222, 205, 129, 85, 167, 233, 144, 29, 185, 73, 26, 147, 139, 24, 248, 190, 176, 125, 151, 196, 124, 189, 237, 33, 234, 132, 54, 67, 226, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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