Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3eded0a3dc913454d92c5f9470853efb9ce6db02d4b09b0f0dcd60c80bde94e2

Tx prefix hash: 10e69071d80bc64471ed92120425550f5ed89a3277d5a1423aefa6f8e1c528ec
Tx public key: a630059cc265971b6718d5f47c42e33172b3e494aec7fb2894bb74858ac36b22
Timestamp: 1728556643 Timestamp [UCT]: 2024-10-10 10:37:23 Age [y:d:h:m:s]: 00:197:00:56:06
Block: 1128491 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140634 RingCT/type: yes/0
Extra: 01a630059cc265971b6718d5f47c42e33172b3e494aec7fb2894bb74858ac36b2202110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f853f694c080a09549eae6ba1f72629a0d29b52be1b6f8487e1a75d8582c5795 0.600000000000 1611310 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": 1128501, "vin": [ { "gen": { "height": 1128491 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f853f694c080a09549eae6ba1f72629a0d29b52be1b6f8487e1a75d8582c5795" } } ], "extra": [ 1, 166, 48, 5, 156, 194, 101, 151, 27, 103, 24, 213, 244, 124, 66, 227, 49, 114, 179, 228, 148, 174, 199, 251, 40, 148, 187, 116, 133, 138, 195, 107, 34, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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