Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40569b26e02fbfbd1fc5848944e61d30eddbeb3e2c4c0c12ee0701988cb21cd6

Tx prefix hash: 196a67ef8e5295d24f5d9f8dba18e7a29b8f6824c06bf73211a4f679c11cdc55
Tx public key: 22a358005c4c234bb8646eb6e647dd505af878a0a47b5cb1d2b4ea6aa9fac69e
Timestamp: 1732821060 Timestamp [UCT]: 2024-11-28 19:11:00 Age [y:d:h:m:s]: 00:150:15:21:40
Block: 1163751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107487 RingCT/type: yes/0
Extra: 0122a358005c4c234bb8646eb6e647dd505af878a0a47b5cb1d2b4ea6aa9fac69e0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9929a5c7af542be9e3e1765a52d485ad6b76ff47ff40a2684dda4aa5419aba6c 0.600000000000 1649420 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": 1163761, "vin": [ { "gen": { "height": 1163751 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9929a5c7af542be9e3e1765a52d485ad6b76ff47ff40a2684dda4aa5419aba6c" } } ], "extra": [ 1, 34, 163, 88, 0, 92, 76, 35, 75, 184, 100, 110, 182, 230, 71, 221, 80, 90, 248, 120, 160, 164, 123, 92, 177, 210, 180, 234, 106, 169, 250, 198, 158, 2, 17, 0, 0, 0, 2, 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