Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce8070b1b726c8d9e2e26891c6d157f4dfcfddaccb4a95e2a3e06a6d84f72fb6

Tx prefix hash: cad110f6e2a7015961ae5d89f38ae925734f06a1692be675cc0032ad7558d4a2
Tx public key: c9e38107c6e85059880973c0a660575fd7463c13de967c61249474f21e6ff1e7
Timestamp: 1718562203 Timestamp [UCT]: 2024-06-16 18:23:23 Age [y:d:h:m:s]: 00:284:19:00:54
Block: 1045651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203495 RingCT/type: yes/0
Extra: 01c9e38107c6e85059880973c0a660575fd7463c13de967c61249474f21e6ff1e702110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 794f00a83278076e372f4fb071abb7bdc4e4765bf1e8d9ee1161429f99345ecc 0.600000000000 1515278 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": 1045661, "vin": [ { "gen": { "height": 1045651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "794f00a83278076e372f4fb071abb7bdc4e4765bf1e8d9ee1161429f99345ecc" } } ], "extra": [ 1, 201, 227, 129, 7, 198, 232, 80, 89, 136, 9, 115, 192, 166, 96, 87, 95, 215, 70, 60, 19, 222, 150, 124, 97, 36, 148, 116, 242, 30, 111, 241, 231, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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