Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e78c8ff183d5cef2bcd6e47396f016752a1be0c32c30a38be1a1fe41f47cacb9

Tx prefix hash: 206667b8345095c6efc7cec3261e991696f67d518fe795d96f48160ce07d9011
Tx public key: 1ced87e9758f25401ac02c1031361af3f44b65f3e4b6e3b975ff04be8367feeb
Timestamp: 1724708968 Timestamp [UCT]: 2024-08-26 21:49:28 Age [y:d:h:m:s]: 00:237:05:59:37
Block: 1096581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169433 RingCT/type: yes/0
Extra: 011ced87e9758f25401ac02c1031361af3f44b65f3e4b6e3b975ff04be8367feeb021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d4f1cb2e93201297c4e9c4557120c0bf05c8dc05c11617c3ee89a8cf3757920 0.600000000000 1571772 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": 1096591, "vin": [ { "gen": { "height": 1096581 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d4f1cb2e93201297c4e9c4557120c0bf05c8dc05c11617c3ee89a8cf3757920" } } ], "extra": [ 1, 28, 237, 135, 233, 117, 143, 37, 64, 26, 192, 44, 16, 49, 54, 26, 243, 244, 75, 101, 243, 228, 182, 227, 185, 117, 255, 4, 190, 131, 103, 254, 235, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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