Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63d3d7d67b9000d36157deadd8d3cc453f4c4bea9456d72fc72e8827db020fb3

Tx prefix hash: 15a93aadf6f689b9f7561dd09d6267de27ffdb093c44298cc4cf4c8c23c2b931
Tx public key: 8b64e6884b3a2076d8902b6c8fa64f78ed71fe7b47bb9cb6d63ecba7471da8a5
Timestamp: 1740073073 Timestamp [UCT]: 2025-02-20 17:37:53 Age [y:d:h:m:s]: 00:229:11:19:24
Block: 1223505 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161711 RingCT/type: yes/0
Extra: 018b64e6884b3a2076d8902b6c8fa64f78ed71fe7b47bb9cb6d63ecba7471da8a5021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1ea45045b778ede9d8ff4658a68ba41dcc91e03a6ecc9b9cc53c12a74842698 0.600000000000 1710362 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": 1223515, "vin": [ { "gen": { "height": 1223505 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1ea45045b778ede9d8ff4658a68ba41dcc91e03a6ecc9b9cc53c12a74842698" } } ], "extra": [ 1, 139, 100, 230, 136, 75, 58, 32, 118, 216, 144, 43, 108, 143, 166, 79, 120, 237, 113, 254, 123, 71, 187, 156, 182, 214, 62, 203, 167, 71, 29, 168, 165, 2, 17, 0, 0, 0, 1, 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