Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4eef4305a34dc69b7d86820566c7746924032271a0ba2913bcdf77d45ea4b866

Tx prefix hash: a392edeb77870511b815230828e2b3675a8467557511fdb43677f2ff893b32a3
Tx public key: e10d9778109e098dc5685df3f86a4b543b0b412fd8f0472b1f62ee2916d7f05c
Timestamp: 1707704738 Timestamp [UCT]: 2024-02-12 02:25:38 Age [y:d:h:m:s]: 01:331:04:48:42
Block: 955609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495564 RingCT/type: yes/0
Extra: 01e10d9778109e098dc5685df3f86a4b543b0b412fd8f0472b1f62ee2916d7f05c02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3e06917077f983cd83b667b4a24810dd81308ef68ca6d0441f4b68bc45bad9d 0.600000000000 1414907 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": 955619, "vin": [ { "gen": { "height": 955609 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3e06917077f983cd83b667b4a24810dd81308ef68ca6d0441f4b68bc45bad9d" } } ], "extra": [ 1, 225, 13, 151, 120, 16, 158, 9, 141, 197, 104, 93, 243, 248, 106, 75, 84, 59, 11, 65, 47, 216, 240, 71, 43, 31, 98, 238, 41, 22, 215, 240, 92, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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