Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74f4cb89c9c41f4bf2ce4654a59e0ed84fe07658d490afbae43611615cd141e6

Tx prefix hash: e74a797a1a324b3c192f65e49e0cc49a73e753094e63b6e78b5b9bea28bffe06
Tx public key: 807c26056ba988a2e4a59e883320de60e2b2f35417b3755d3eee73bd0160cc4b
Timestamp: 1752252500 Timestamp [UCT]: 2025-07-11 16:48:20 Age [y:d:h:m:s]: 00:182:00:35:26
Block: 1323389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128803 RingCT/type: yes/0
Extra: 01807c26056ba988a2e4a59e883320de60e2b2f35417b3755d3eee73bd0160cc4b02110000000743846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8062a1791204b4ed21bdbb0564f89cef089615f7549dbc07c2f7a4bd4c48de2 0.600000000000 1811126 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": 1323399, "vin": [ { "gen": { "height": 1323389 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8062a1791204b4ed21bdbb0564f89cef089615f7549dbc07c2f7a4bd4c48de2" } } ], "extra": [ 1, 128, 124, 38, 5, 107, 169, 136, 162, 228, 165, 158, 136, 51, 32, 222, 96, 226, 178, 243, 84, 23, 179, 117, 93, 62, 238, 115, 189, 1, 96, 204, 75, 2, 17, 0, 0, 0, 7, 67, 132, 109, 102, 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