Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a1c7767a95b6c1f727555d5885c5468d5a000e7fdb3a4ff16c9f5be73d7d0da

Tx prefix hash: 554ec93eac7ce9235f532160f54220ca1ceed114136220a27b6613abfe75fccb
Tx public key: 339857c7f89e10c2df48876c1ec62017e07dcbf764e67ba8e52be0af8b52827f
Timestamp: 1712301083 Timestamp [UCT]: 2024-04-05 07:11:23 Age [y:d:h:m:s]: 01:216:16:33:50
Block: 993695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413576 RingCT/type: yes/0
Extra: 01339857c7f89e10c2df48876c1ec62017e07dcbf764e67ba8e52be0af8b52827f02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a160013250bdfdaf480682b6dddbc5b0e49ba6b740a3f2e7048918fb9f1c862f 0.600000000000 1454083 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": 993705, "vin": [ { "gen": { "height": 993695 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a160013250bdfdaf480682b6dddbc5b0e49ba6b740a3f2e7048918fb9f1c862f" } } ], "extra": [ 1, 51, 152, 87, 199, 248, 158, 16, 194, 223, 72, 135, 108, 30, 198, 32, 23, 224, 125, 203, 247, 100, 230, 123, 168, 229, 43, 224, 175, 139, 82, 130, 127, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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