Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 387ea4f389d1434e2081c7aa8345ffdca6b965c6370046d5d8addb61ff236923

Tx prefix hash: 70bf5165eaf046de41cf0a257e1761bde4b41239c91cc341e83cb6330b278006
Tx public key: 123b1856d0bd32f8aac3715362f489c04b1201b74f4d4952a57ce2dd70c3aac2
Timestamp: 1738605700 Timestamp [UCT]: 2025-02-03 18:01:40 Age [y:d:h:m:s]: 00:288:20:06:53
Block: 1211366 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204205 RingCT/type: yes/0
Extra: 01123b1856d0bd32f8aac3715362f489c04b1201b74f4d4952a57ce2dd70c3aac2021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f1fe5af1d4aaa2b2981cb84f123db6f515d7c6dace8e1a3f3b9f65c3352672b 0.600000000000 1698127 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": 1211376, "vin": [ { "gen": { "height": 1211366 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f1fe5af1d4aaa2b2981cb84f123db6f515d7c6dace8e1a3f3b9f65c3352672b" } } ], "extra": [ 1, 18, 59, 24, 86, 208, 189, 50, 248, 170, 195, 113, 83, 98, 244, 137, 192, 75, 18, 1, 183, 79, 77, 73, 82, 165, 124, 226, 221, 112, 195, 170, 194, 2, 17, 0, 0, 0, 3, 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