Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 248bbadc4cff0cdb87437c5c8ddcdee9a2ba6088783723fa797562b9b5aa5714

Tx prefix hash: 598c0914956357d268a4ade5702139c50d9bf63aa3ed9c806e68305f35133e56
Tx public key: 055b2772e2b2b57b7d798ea84acc7e16e27a602dcb77067b84c81f006ef03968
Timestamp: 1744959410 Timestamp [UCT]: 2025-04-18 06:56:50 Age [y:d:h:m:s]: 00:217:14:23:28
Block: 1263973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153244 RingCT/type: yes/0
Extra: 01055b2772e2b2b57b7d798ea84acc7e16e27a602dcb77067b84c81f006ef039680211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64c75c04ad9011fe51cdc8bce951a1052fae1565da37b2c43ac2c688bc45d5bf 0.600000000000 1751166 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": 1263983, "vin": [ { "gen": { "height": 1263973 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64c75c04ad9011fe51cdc8bce951a1052fae1565da37b2c43ac2c688bc45d5bf" } } ], "extra": [ 1, 5, 91, 39, 114, 226, 178, 181, 123, 125, 121, 142, 168, 74, 204, 126, 22, 226, 122, 96, 45, 203, 119, 6, 123, 132, 200, 31, 0, 110, 240, 57, 104, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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