Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c926944d119a4e5abb1760536c6d0fb848d4e9cef74f18da00b04555233d0f01

Tx prefix hash: 1331b4aa6da8907469685c647a5844b750b6d2abefc97101f7edbfa52d1a9cb0
Tx public key: 8fe5f62494c116ac718510e272191d24b7db04825ac5b9c41627ff7d8ccff0ea
Timestamp: 1706185475 Timestamp [UCT]: 2024-01-25 12:24:35 Age [y:d:h:m:s]: 00:336:19:51:46
Block: 942998 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241164 RingCT/type: yes/0
Extra: 018fe5f62494c116ac718510e272191d24b7db04825ac5b9c41627ff7d8ccff0ea0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 929e3ad7962b73e6ac6e4d3b5bc44b4cd2a508479b1a716a0bc9d8da20034038 0.600000000000 1401196 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": 943008, "vin": [ { "gen": { "height": 942998 } } ], "vout": [ { "amount": 600000000, "target": { "key": "929e3ad7962b73e6ac6e4d3b5bc44b4cd2a508479b1a716a0bc9d8da20034038" } } ], "extra": [ 1, 143, 229, 246, 36, 148, 193, 22, 172, 113, 133, 16, 226, 114, 25, 29, 36, 183, 219, 4, 130, 90, 197, 185, 196, 22, 39, 255, 125, 140, 207, 240, 234, 2, 17, 0, 0, 0, 4, 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