Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a05b298ffc705cde307c9be43185b5601d9bae07202fecdd24b43d566eff3e4e

Tx prefix hash: ff485902e583ffaddb135859aa624b48a1b12376a6334356634208db2732b531
Tx public key: 82ea08c1e504515f55ecd2c89f9f3b107c0e94552b0a2bb3f3b8e8c9b177e8ab
Timestamp: 1729392704 Timestamp [UCT]: 2024-10-20 02:51:44 Age [y:d:h:m:s]: 01:021:01:14:22
Block: 1135418 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273412 RingCT/type: yes/0
Extra: 0182ea08c1e504515f55ecd2c89f9f3b107c0e94552b0a2bb3f3b8e8c9b177e8ab021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e43e6951bcfb11fef1b333f686d9d53948410773451b1e2f394fba082077854 0.600000000000 1618755 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": 1135428, "vin": [ { "gen": { "height": 1135418 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e43e6951bcfb11fef1b333f686d9d53948410773451b1e2f394fba082077854" } } ], "extra": [ 1, 130, 234, 8, 193, 229, 4, 81, 95, 85, 236, 210, 200, 159, 159, 59, 16, 124, 14, 148, 85, 43, 10, 43, 179, 243, 184, 232, 201, 177, 119, 232, 171, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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