Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: feef5c449e8c952e8c2883ad77f3964e68902bd4e584161b4469bf7e52457677

Tx prefix hash: dc3d56771444438712dedc6f6329a39dfd3a54a767c3ae04c9004d5aa0d753ef
Tx public key: 51fecab4f3c987988a488fe5b30c511bb8371c1fc39e126d48b7733fe5cd0b9e
Timestamp: 1737151917 Timestamp [UCT]: 2025-01-17 22:11:57 Age [y:d:h:m:s]: 00:059:15:18:33
Block: 1199604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42411 RingCT/type: yes/0
Extra: 0151fecab4f3c987988a488fe5b30c511bb8371c1fc39e126d48b7733fe5cd0b9e021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5c8e409ee81993c9c97e07f902039f2eba0853dcfe4fd8c6c75a5627a3989e8 0.600000000000 1686237 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": 1199614, "vin": [ { "gen": { "height": 1199604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5c8e409ee81993c9c97e07f902039f2eba0853dcfe4fd8c6c75a5627a3989e8" } } ], "extra": [ 1, 81, 254, 202, 180, 243, 201, 135, 152, 138, 72, 143, 229, 179, 12, 81, 27, 184, 55, 28, 31, 195, 158, 18, 109, 72, 183, 115, 63, 229, 205, 11, 158, 2, 17, 0, 0, 0, 2, 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