Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e26ffe6eeb1a1145d931b068fc59dc6ecb31062d28e11168eb97c3fed8d0fca3

Tx prefix hash: 108e400096291d5e8f8d6f96984d0aa18cc56f5aa933f437c413582e44eb6f7b
Tx public key: 0c0c8b800fea5a89e884ff7f52f103c0f2bca6d06988dc121e8f759edf667d1e
Timestamp: 1700753024 Timestamp [UCT]: 2023-11-23 15:23:44 Age [y:d:h:m:s]: 01:056:17:31:42
Block: 897988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301936 RingCT/type: yes/0
Extra: 010c0c8b800fea5a89e884ff7f52f103c0f2bca6d06988dc121e8f759edf667d1e02110000000333af99f4000000000000000000

1 output(s) for total of 0.649520660000 dcy

stealth address amount amount idx
00: ccf21f7f60d96e6f01c5870c2e9fcb59734918633e035d9e7dce86e41ed5a841 0.649520660000 1354391 of 0

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": 897998, "vin": [ { "gen": { "height": 897988 } } ], "vout": [ { "amount": 649520660, "target": { "key": "ccf21f7f60d96e6f01c5870c2e9fcb59734918633e035d9e7dce86e41ed5a841" } } ], "extra": [ 1, 12, 12, 139, 128, 15, 234, 90, 137, 232, 132, 255, 127, 82, 241, 3, 192, 242, 188, 166, 208, 105, 136, 220, 18, 30, 143, 117, 158, 223, 102, 125, 30, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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