Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cdc5c89d2f57c6963d1c33ee13053d5bd5340e55e2ba34e1719a328562bd29e2

Tx prefix hash: 1b9eee657ffda8a4d9f2ec5a4da3f9d647f1b3c98f6f337603df5f0b592a61f5
Tx public key: fcd912e1cc98eafcbd33cef3f22fa55307c2576b299b78f02136d0172342b147
Timestamp: 1705382430 Timestamp [UCT]: 2024-01-16 05:20:30 Age [y:d:h:m:s]: 01:098:06:38:42
Block: 936346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331354 RingCT/type: yes/0
Extra: 01fcd912e1cc98eafcbd33cef3f22fa55307c2576b299b78f02136d0172342b1470211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d63ab70e1713444d9349fabab743d28bd8080c825e35ee6db2379e9a03070db6 0.600000000000 1394370 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": 936356, "vin": [ { "gen": { "height": 936346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d63ab70e1713444d9349fabab743d28bd8080c825e35ee6db2379e9a03070db6" } } ], "extra": [ 1, 252, 217, 18, 225, 204, 152, 234, 252, 189, 51, 206, 243, 242, 47, 165, 83, 7, 194, 87, 107, 41, 155, 120, 240, 33, 54, 208, 23, 35, 66, 177, 71, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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