Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf03ee038c32e4ee7fe201c3c41fefe6858312da4e16d14610ec5c4365724cd3

Tx prefix hash: 9915b8619fcd0197445c247df1ab6873cecf943f190c0a1e38e490bd9d122c6a
Tx public key: ef293435d6f5f9120612b973fd1a561187c80bba4f781a9a40ef7a90a6f34dc6
Timestamp: 1716886364 Timestamp [UCT]: 2024-05-28 08:52:44 Age [y:d:h:m:s]: 00:311:12:39:53
Block: 1031755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222632 RingCT/type: yes/0
Extra: 01ef293435d6f5f9120612b973fd1a561187c80bba4f781a9a40ef7a90a6f34dc60211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d906f7d54f44b8ecab8b03c0d6a7287c9dd4cbbcb7813510da71dcc9f3cccad1 0.600000000000 1500204 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": 1031765, "vin": [ { "gen": { "height": 1031755 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d906f7d54f44b8ecab8b03c0d6a7287c9dd4cbbcb7813510da71dcc9f3cccad1" } } ], "extra": [ 1, 239, 41, 52, 53, 214, 245, 249, 18, 6, 18, 185, 115, 253, 26, 86, 17, 135, 200, 11, 186, 79, 120, 26, 154, 64, 239, 122, 144, 166, 243, 77, 198, 2, 17, 0, 0, 0, 3, 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