Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1607a0ab32fea382eabb17b8b79a76a8011f5ee2b8441e37dfb1e04e2df0d8aa

Tx prefix hash: 43820ff1e66f75e0bf36537a80639840bbe6e1480cd1af8a9824348c45e87341
Tx public key: c19a15f1f2876d0f9ebeaf19a8b52acde31a11966e1cc9512e94080d8ac9acab
Timestamp: 1720962156 Timestamp [UCT]: 2024-07-14 13:02:36 Age [y:d:h:m:s]: 00:262:13:29:27
Block: 1065544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187558 RingCT/type: yes/0
Extra: 01c19a15f1f2876d0f9ebeaf19a8b52acde31a11966e1cc9512e94080d8ac9acab02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6853133efeb9899fa2634a125d7ce293ec5041cb72c18c16dfbd4a32ddae5c9 0.600000000000 1536091 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": 1065554, "vin": [ { "gen": { "height": 1065544 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6853133efeb9899fa2634a125d7ce293ec5041cb72c18c16dfbd4a32ddae5c9" } } ], "extra": [ 1, 193, 154, 21, 241, 242, 135, 109, 15, 158, 190, 175, 25, 168, 181, 42, 205, 227, 26, 17, 150, 110, 28, 201, 81, 46, 148, 8, 13, 138, 201, 172, 171, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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