Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ddb3023d5ef7500f108182e0527db1d5cb9aa6b562abd3dc94cdb8a04cfe5c7

Tx prefix hash: 4772d3ad9cb05f491d875121e6893ed46d454fa7e498e612fa20875a9eec1de0
Tx public key: 6b21dfb083328762d497a14f221e8cda7bd242d5c73774179ab0e62cc8976075
Timestamp: 1718671504 Timestamp [UCT]: 2024-06-18 00:45:04 Age [y:d:h:m:s]: 00:328:22:26:03
Block: 1046551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235070 RingCT/type: yes/0
Extra: 016b21dfb083328762d497a14f221e8cda7bd242d5c73774179ab0e62cc897607502110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac531f0a9ef17d1a40117892c4fe4bc37a5a7cac1312d7433ac30d4eac97379b 0.600000000000 1516366 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": 1046561, "vin": [ { "gen": { "height": 1046551 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac531f0a9ef17d1a40117892c4fe4bc37a5a7cac1312d7433ac30d4eac97379b" } } ], "extra": [ 1, 107, 33, 223, 176, 131, 50, 135, 98, 212, 151, 161, 79, 34, 30, 140, 218, 123, 210, 66, 213, 199, 55, 116, 23, 154, 176, 230, 44, 200, 151, 96, 117, 2, 17, 0, 0, 0, 5, 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