Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12ec016703f545d4ca36be29f2163bc58b726646f5884bd3d1e1f2e31570c8fd

Tx prefix hash: 8a7e6d6115b17c0ec54b2e304e8d1305d1e1b02adbe5d56a7b757105a7443275
Tx public key: 0e851f3537f9adc52d8f7829ff34eaf4564082936793c1cfd0f42d88de88eef2
Timestamp: 1736650946 Timestamp [UCT]: 2025-01-12 03:02:26 Age [y:d:h:m:s]: 00:065:07:01:53
Block: 1195454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46454 RingCT/type: yes/0
Extra: 010e851f3537f9adc52d8f7829ff34eaf4564082936793c1cfd0f42d88de88eef20211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9cc80fd76ab3d71cb3faeae27e9d1637169ebd40aad6ca0ba3ab59c4d02d3e0 0.600000000000 1682045 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": 1195464, "vin": [ { "gen": { "height": 1195454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9cc80fd76ab3d71cb3faeae27e9d1637169ebd40aad6ca0ba3ab59c4d02d3e0" } } ], "extra": [ 1, 14, 133, 31, 53, 55, 249, 173, 197, 45, 143, 120, 41, 255, 52, 234, 244, 86, 64, 130, 147, 103, 147, 193, 207, 208, 244, 45, 136, 222, 136, 238, 242, 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