Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f1f7bbd053f7376b5050a1263b345b871c9efd1c974a5a30d25bb931ae55443

Tx prefix hash: dbb1461df155573b1877bfa9b9de194f6391bd14d2cdc50c2327292def13df14
Tx public key: e95720c8e676e617d2f9078f30007ff45d899f2bd63c0861b351d87eeb2e6dad
Timestamp: 1702197315 Timestamp [UCT]: 2023-12-10 08:35:15 Age [y:d:h:m:s]: 01:119:12:43:44
Block: 909969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346545 RingCT/type: yes/0
Extra: 01e95720c8e676e617d2f9078f30007ff45d899f2bd63c0861b351d87eeb2e6dad0211000000034b8f5122000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f7c81924aa7fb43b61bcd9083ce5eed7d3ea48a35a2ae19c76f44ab854fece4 0.600000000000 1367106 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": 909979, "vin": [ { "gen": { "height": 909969 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f7c81924aa7fb43b61bcd9083ce5eed7d3ea48a35a2ae19c76f44ab854fece4" } } ], "extra": [ 1, 233, 87, 32, 200, 230, 118, 230, 23, 210, 249, 7, 143, 48, 0, 127, 244, 93, 137, 159, 43, 214, 60, 8, 97, 179, 81, 216, 126, 235, 46, 109, 173, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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