Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f9db773c408aaf700367b8351dba49e6b6f531a91658e8d4f3f3a4c6685bdbd

Tx prefix hash: d17b9786d6fda61aa054a6ca495a304044c206a7d2ca282143b8325fea2dc23a
Tx public key: 844c0e6af24737dc979252bf719256311cc8ead8a6b411a405e600f4f31b5b91
Timestamp: 1746341762 Timestamp [UCT]: 2025-05-04 06:56:02 Age [y:d:h:m:s]: 00:201:05:05:53
Block: 1275416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141518 RingCT/type: yes/0
Extra: 01844c0e6af24737dc979252bf719256311cc8ead8a6b411a405e600f4f31b5b910211000000021f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0cc15d304b2fa0bbcf4527462ec520343de0ce4c5e2c45993c15247cfa623819 0.600000000000 1762727 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": 1275426, "vin": [ { "gen": { "height": 1275416 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cc15d304b2fa0bbcf4527462ec520343de0ce4c5e2c45993c15247cfa623819" } } ], "extra": [ 1, 132, 76, 14, 106, 242, 71, 55, 220, 151, 146, 82, 191, 113, 146, 86, 49, 28, 200, 234, 216, 166, 180, 17, 164, 5, 230, 0, 244, 243, 27, 91, 145, 2, 17, 0, 0, 0, 2, 31, 144, 81, 122, 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