Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b84f250e030dbf34c0f4f17de191e99e96de592352271631693a7379e7f2ed71

Tx prefix hash: 2692b62be928d4fa86451966d3fe585aa63d74ee0556295b5729d5d61499b05e
Tx public key: cf4d160647254f5f6fca18fd061f94dd4cf787c758ae7e9a5fa5f350080059ad
Timestamp: 1744568823 Timestamp [UCT]: 2025-04-13 18:27:03 Age [y:d:h:m:s]: 00:268:03:18:53
Block: 1260742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189429 RingCT/type: yes/0
Extra: 01cf4d160647254f5f6fca18fd061f94dd4cf787c758ae7e9a5fa5f350080059ad021100000007dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f562c990ada710f7a90df75704110540d925de932b66f0e53ab95c9519b7f7b 0.600000000000 1747903 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": 1260752, "vin": [ { "gen": { "height": 1260742 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f562c990ada710f7a90df75704110540d925de932b66f0e53ab95c9519b7f7b" } } ], "extra": [ 1, 207, 77, 22, 6, 71, 37, 79, 95, 111, 202, 24, 253, 6, 31, 148, 221, 76, 247, 135, 199, 88, 174, 126, 154, 95, 165, 243, 80, 8, 0, 89, 173, 2, 17, 0, 0, 0, 7, 219, 181, 113, 193, 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