Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9909eb8a69e1cc4af02de93998c7c5c9b03d15a1f52e0161fee0b4e5086eebcc

Tx prefix hash: 1a589abf9e813af738e3f4ccd56b79f860e4569150f6f7855b6a09d05c41bef2
Tx public key: 4c137b8ff0ed1002e1c6f6b384855d47470c95aec8ce10eba928701e482168d1
Timestamp: 1704541392 Timestamp [UCT]: 2024-01-06 11:43:12 Age [y:d:h:m:s]: 01:168:01:17:19
Block: 929371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381081 RingCT/type: yes/0
Extra: 014c137b8ff0ed1002e1c6f6b384855d47470c95aec8ce10eba928701e482168d10211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c59bffa3b7be5ca304c2602e026752eabd1b74f92fdbb5ceacf4529d0011d9c8 0.600000000000 1387243 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": 929381, "vin": [ { "gen": { "height": 929371 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c59bffa3b7be5ca304c2602e026752eabd1b74f92fdbb5ceacf4529d0011d9c8" } } ], "extra": [ 1, 76, 19, 123, 143, 240, 237, 16, 2, 225, 198, 246, 179, 132, 133, 93, 71, 71, 12, 149, 174, 200, 206, 16, 235, 169, 40, 112, 30, 72, 33, 104, 209, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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