Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af7b7564b1aae3455501750eb12f2380d27c85fb726c13c1f9a424dd2cc9ed80

Tx prefix hash: 5ffd321d8e6950be887061b40a1805943ebb365f41094c49cce5fdba4df14eb3
Tx public key: 356ac6c84ab782a96db0bfd0a4ee7e674033973de8269851d3fb49c19c0e9202
Timestamp: 1734048753 Timestamp [UCT]: 2024-12-13 00:12:33 Age [y:d:h:m:s]: 00:189:20:36:18
Block: 1173935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135347 RingCT/type: yes/0
Extra: 01356ac6c84ab782a96db0bfd0a4ee7e674033973de8269851d3fb49c19c0e9202021100000001a2d75f44000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e275c62ac89b2d4847156fe5e97b4a6c6a4b82a22758b99656c2fda9eade35c5 0.600000000000 1660024 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": 1173945, "vin": [ { "gen": { "height": 1173935 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e275c62ac89b2d4847156fe5e97b4a6c6a4b82a22758b99656c2fda9eade35c5" } } ], "extra": [ 1, 53, 106, 198, 200, 74, 183, 130, 169, 109, 176, 191, 208, 164, 238, 126, 103, 64, 51, 151, 61, 232, 38, 152, 81, 211, 251, 73, 193, 156, 14, 146, 2, 2, 17, 0, 0, 0, 1, 162, 215, 95, 68, 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