Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ec9acfc3d2ad996f78eb757b932264bed58622e1e832ed8d74395a3afaa2d12

Tx prefix hash: 7862c7eb6cb0c397d8069b38d017a679a56f6af1f53db01098d0a7d8445f9a83
Tx public key: 91cd1dd9533e20f3ebd0bc466e29bf4071754d0f219210f81a1a429dd6a921b5
Timestamp: 1744432636 Timestamp [UCT]: 2025-04-12 04:37:16 Age [y:d:h:m:s]: 00:293:04:27:09
Block: 1259608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207196 RingCT/type: yes/0
Extra: 0191cd1dd9533e20f3ebd0bc466e29bf4071754d0f219210f81a1a429dd6a921b50211000000036c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b1dd76d57c47387ee2395a3fe226f79db8c79962c38c9bd55dc7ff0bdf321db 0.600000000000 1746755 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": 1259618, "vin": [ { "gen": { "height": 1259608 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b1dd76d57c47387ee2395a3fe226f79db8c79962c38c9bd55dc7ff0bdf321db" } } ], "extra": [ 1, 145, 205, 29, 217, 83, 62, 32, 243, 235, 208, 188, 70, 110, 41, 191, 64, 113, 117, 77, 15, 33, 146, 16, 248, 26, 26, 66, 157, 214, 169, 33, 181, 2, 17, 0, 0, 0, 3, 108, 152, 170, 61, 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