Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92b4d4dd7c27f0107d23424697bdb635340d209acdaf1a868d728bd9d68fb021

Tx prefix hash: 65e00de245328202b1b5f71ba6d2ba462d3da3cf5e0b3263bbae85577ebfae74
Tx public key: b748fa560aa34b38b325f0c20eaea1c1cf7d8067e88a633368f3b9ecaf68fb91
Timestamp: 1737801494 Timestamp [UCT]: 2025-01-25 10:38:14 Age [y:d:h:m:s]: 00:172:18:22:15
Block: 1204944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122242 RingCT/type: yes/0
Extra: 01b748fa560aa34b38b325f0c20eaea1c1cf7d8067e88a633368f3b9ecaf68fb91021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08e21beb7f5ad7993801e935479febf8143c0f569f4232297e5f902bd723685c 0.600000000000 1691639 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": 1204954, "vin": [ { "gen": { "height": 1204944 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08e21beb7f5ad7993801e935479febf8143c0f569f4232297e5f902bd723685c" } } ], "extra": [ 1, 183, 72, 250, 86, 10, 163, 75, 56, 179, 37, 240, 194, 14, 174, 161, 193, 207, 125, 128, 103, 232, 138, 99, 51, 104, 243, 185, 236, 175, 104, 251, 145, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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