Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4bfc08e8eb6782b4100bee927288a3d6fdb085d35ba0ff58bbf8119d21d813a

Tx prefix hash: 7e39bf3d8daaa60a2a74ba99abb85fb40d93f4ffecf4bf6f3031ea50cf3d2dbe
Tx public key: ecf39ac67d4a8e28e7f917354febba58bfdf7c16a093807cb2784626f9810813
Timestamp: 1681469100 Timestamp [UCT]: 2023-04-14 10:45:00 Age [y:d:h:m:s]: 01:358:20:03:46
Block: 738355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 517742 RingCT/type: yes/0
Extra: 01ecf39ac67d4a8e28e7f917354febba58bfdf7c16a093807cb2784626f9810813021100000006b3164c24000000000000000000

1 output(s) for total of 2.195450246000 dcy

stealth address amount amount idx
00: cfd6a28b5cc02d04b7c13bcd9a48572884848d88cd8dcfceef232fbde8761545 2.195450246000 1185034 of 0

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": 738365, "vin": [ { "gen": { "height": 738355 } } ], "vout": [ { "amount": 2195450246, "target": { "key": "cfd6a28b5cc02d04b7c13bcd9a48572884848d88cd8dcfceef232fbde8761545" } } ], "extra": [ 1, 236, 243, 154, 198, 125, 74, 142, 40, 231, 249, 23, 53, 79, 235, 186, 88, 191, 223, 124, 22, 160, 147, 128, 124, 178, 120, 70, 38, 249, 129, 8, 19, 2, 17, 0, 0, 0, 6, 179, 22, 76, 36, 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