Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c882fe7ffcd2b50fe14b05c8fb64c03ece9fe775367ea00fd5dd6519e01aec3

Tx prefix hash: c7fc812bb310a268611e9cde7c913120f8fe7a0569015dfadf1b568cd501287b
Tx public key: abb3b0bbbd7458c6c20174d8d1b171797fc6436beea53a7014e392c5926249b9
Timestamp: 1714392904 Timestamp [UCT]: 2024-04-29 12:15:04 Age [y:d:h:m:s]: 00:344:12:23:24
Block: 1011068 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246271 RingCT/type: yes/0
Extra: 01abb3b0bbbd7458c6c20174d8d1b171797fc6436beea53a7014e392c5926249b90211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1169e1240f343506caa5dd1d73813e3a5bf0e2ee4d993cdee3493fdc515bd127 0.600000000000 1473196 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": 1011078, "vin": [ { "gen": { "height": 1011068 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1169e1240f343506caa5dd1d73813e3a5bf0e2ee4d993cdee3493fdc515bd127" } } ], "extra": [ 1, 171, 179, 176, 187, 189, 116, 88, 198, 194, 1, 116, 216, 209, 177, 113, 121, 127, 198, 67, 107, 238, 165, 58, 112, 20, 227, 146, 197, 146, 98, 73, 185, 2, 17, 0, 0, 0, 6, 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