Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eea716c2690f6cb643577991bcb52ebd6e94a7ad0ab09308447dc7b2c2e74b42

Tx prefix hash: 271870bc95d3c9e73ace60f25cbbd1ec3f12965b6232c26511504b7fdd96325a
Tx public key: 41d9f23d9cb35935dfed619502fce2a5bd231df2f73bc628b7a6bcbab85128b8
Timestamp: 1705657206 Timestamp [UCT]: 2024-01-19 09:40:06 Age [y:d:h:m:s]: 01:147:20:00:26
Block: 938612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366718 RingCT/type: yes/0
Extra: 0141d9f23d9cb35935dfed619502fce2a5bd231df2f73bc628b7a6bcbab85128b802110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34a83b9f60497f9dec3c22097edb02dc55fa8c079e0f6219c89622614d94790a 0.600000000000 1396682 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": 938622, "vin": [ { "gen": { "height": 938612 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34a83b9f60497f9dec3c22097edb02dc55fa8c079e0f6219c89622614d94790a" } } ], "extra": [ 1, 65, 217, 242, 61, 156, 179, 89, 53, 223, 237, 97, 149, 2, 252, 226, 165, 189, 35, 29, 242, 247, 59, 198, 40, 183, 166, 188, 186, 184, 81, 40, 184, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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