Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a06b2b8ea65e9776b78c677798cf6d24634c96c18a2ed9b5261b7faba4d8b38

Tx prefix hash: 0bfaf09ffac1aebcb30bb704f1aeeaa0fc5f50137c9d6a4629d1f1450c457ff5
Tx public key: 5ca6fb07ad8c62083ad5ab6f112eb05999e3761b721124e35d8c9ba581e3b83a
Timestamp: 1726845067 Timestamp [UCT]: 2024-09-20 15:11:07 Age [y:d:h:m:s]: 00:125:17:05:52
Block: 1114304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89856 RingCT/type: yes/0
Extra: 015ca6fb07ad8c62083ad5ab6f112eb05999e3761b721124e35d8c9ba581e3b83a021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5d1c79aae0f86873429782f837f4f15cb6d120ae340b0de4067c687871c1d2d 0.600000000000 1594103 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": 1114314, "vin": [ { "gen": { "height": 1114304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5d1c79aae0f86873429782f837f4f15cb6d120ae340b0de4067c687871c1d2d" } } ], "extra": [ 1, 92, 166, 251, 7, 173, 140, 98, 8, 58, 213, 171, 111, 17, 46, 176, 89, 153, 227, 118, 27, 114, 17, 36, 227, 93, 140, 155, 165, 129, 227, 184, 58, 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