Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cf87d1e40922f98d3796f0e72d548fb1937e815bd2f4f69497abaf8bdabdabb

Tx prefix hash: 3fbea452e02b09519bae278e67d87c89aa6e72c63b1bd4b047a850a05d9e5ff7
Tx public key: 88d6199f00321e4429b8a496b02df04652a93276fc6ab1b3387dd25cfa9b46de
Timestamp: 1708899931 Timestamp [UCT]: 2024-02-25 22:25:31 Age [y:d:h:m:s]: 01:089:00:12:14
Block: 965534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324664 RingCT/type: yes/0
Extra: 0188d6199f00321e4429b8a496b02df04652a93276fc6ab1b3387dd25cfa9b46de0211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41613b8b2dd7688ea690a09981e276139222b442fd1146d61c030c8fbe4c0e50 0.600000000000 1425287 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": 965544, "vin": [ { "gen": { "height": 965534 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41613b8b2dd7688ea690a09981e276139222b442fd1146d61c030c8fbe4c0e50" } } ], "extra": [ 1, 136, 214, 25, 159, 0, 50, 30, 68, 41, 184, 164, 150, 176, 45, 240, 70, 82, 169, 50, 118, 252, 106, 177, 179, 56, 125, 210, 92, 250, 155, 70, 222, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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