Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9d1769fe2e9c6dbf3c52c1a00c3f3b01c3897d62d65ef465d67366067cadc4f

Tx prefix hash: 3f1de1fb386be7fca115d13c05f5ba34009249f1ba9ec7a84f864262638298ff
Tx public key: 014e3a646838730ae1e71d20ef8003dc9ad20a0703132d9a0bc728688a5701ca
Timestamp: 1710923223 Timestamp [UCT]: 2024-03-20 08:27:03 Age [y:d:h:m:s]: 01:016:04:44:45
Block: 982325 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272533 RingCT/type: yes/0
Extra: 01014e3a646838730ae1e71d20ef8003dc9ad20a0703132d9a0bc728688a5701ca0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc697c3f5740d8b52baec6004c7e0dc7974f9f2db02a2509073006a322158fb0 0.600000000000 1442430 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": 982335, "vin": [ { "gen": { "height": 982325 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc697c3f5740d8b52baec6004c7e0dc7974f9f2db02a2509073006a322158fb0" } } ], "extra": [ 1, 1, 78, 58, 100, 104, 56, 115, 10, 225, 231, 29, 32, 239, 128, 3, 220, 154, 210, 10, 7, 3, 19, 45, 154, 11, 199, 40, 104, 138, 87, 1, 202, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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