Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 338c68ccb65ddfd577491229ca4a8cc860b0e36763113c293065c634d4e4960f

Tx prefix hash: 198f423b02f1c1019b76d7e9bc92a539040be7799f1079d74ea0b5c6a4f4e3d0
Tx public key: e68ea2f1743a27dd3ef8c1c02bb6a07fc898ddd6caf3814bb67763a359503f18
Timestamp: 1740332867 Timestamp [UCT]: 2025-02-23 17:47:47 Age [y:d:h:m:s]: 00:226:14:02:15
Block: 1225654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159651 RingCT/type: yes/0
Extra: 01e68ea2f1743a27dd3ef8c1c02bb6a07fc898ddd6caf3814bb67763a359503f18021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78fb5d48cf38ad6b54d56f1bf413ae69c00e066d180ec41193367fd346b878e5 0.600000000000 1712521 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": 1225664, "vin": [ { "gen": { "height": 1225654 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78fb5d48cf38ad6b54d56f1bf413ae69c00e066d180ec41193367fd346b878e5" } } ], "extra": [ 1, 230, 142, 162, 241, 116, 58, 39, 221, 62, 248, 193, 192, 43, 182, 160, 127, 200, 152, 221, 214, 202, 243, 129, 75, 182, 119, 99, 163, 89, 80, 63, 24, 2, 17, 0, 0, 0, 5, 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