Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2eb5209b3b7333f51b0d9bd1d40d9ec9be35c0d999af0661d25a6967dc8a8477

Tx prefix hash: ca86ac5cdcf5e7143eaf8dd0701766371eb66e0c2ccab3e8101985f7aaefea1a
Tx public key: 211130ff911ef9896a717aea583cbcc3ae3096a8158f56e97d44e63d1d051f28
Timestamp: 1740298942 Timestamp [UCT]: 2025-02-23 08:22:22 Age [y:d:h:m:s]: 00:344:00:48:25
Block: 1225370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243574 RingCT/type: yes/0
Extra: 01211130ff911ef9896a717aea583cbcc3ae3096a8158f56e97d44e63d1d051f28021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c5e72bd831640880bfdb5cf3745d47fbdc4bae5f20237253c1457907c0a00cf 0.600000000000 1712235 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": 1225380, "vin": [ { "gen": { "height": 1225370 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c5e72bd831640880bfdb5cf3745d47fbdc4bae5f20237253c1457907c0a00cf" } } ], "extra": [ 1, 33, 17, 48, 255, 145, 30, 249, 137, 106, 113, 122, 234, 88, 60, 188, 195, 174, 48, 150, 168, 21, 143, 86, 233, 125, 68, 230, 61, 29, 5, 31, 40, 2, 17, 0, 0, 0, 4, 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