Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10b6b2269d86de07285d96080cd70b1b5e53b2f4b83a43f4f63d6ad29dc91a98

Tx prefix hash: c79235e96948ae6be7b7c13915cb5d1ffee2dc161d6e0fea4f6d624cde47602c
Tx public key: 7919c9beb17a2f22e8ac17621883e643dba954c548fb83e94f51fe80ab4b5493
Timestamp: 1712848629 Timestamp [UCT]: 2024-04-11 15:17:09 Age [y:d:h:m:s]: 00:362:05:35:07
Block: 998241 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258987 RingCT/type: yes/0
Extra: 017919c9beb17a2f22e8ac17621883e643dba954c548fb83e94f51fe80ab4b54930211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f58cd6a1da9393e63eacc79829cf3f32ede41350cf89d1214227e1c206dc42df 0.600000000000 1458687 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": 998251, "vin": [ { "gen": { "height": 998241 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f58cd6a1da9393e63eacc79829cf3f32ede41350cf89d1214227e1c206dc42df" } } ], "extra": [ 1, 121, 25, 201, 190, 177, 122, 47, 34, 232, 172, 23, 98, 24, 131, 230, 67, 219, 169, 84, 197, 72, 251, 131, 233, 79, 81, 254, 128, 171, 75, 84, 147, 2, 17, 0, 0, 0, 3, 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