Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e87e3cb4aaaeae7769835a238d69e96d48618c0316fd57bac80c5280bd6d3af

Tx prefix hash: 0cf6fd5e106743860a4b21a15b820dc5b66f24ecaa811d5bcb62f05b200335b2
Tx public key: 1bfdf06029b5a4bbe56649fe67284729681293196bc59caefce8bdef32715415
Timestamp: 1700339750 Timestamp [UTC]: 2023-11-18 20:35:50 Age [y:d:h:m:s]: 02:179:06:35:30
Block: 894560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 640265 RingCT/type: yes/0
Extra: 011bfdf06029b5a4bbe56649fe67284729681293196bc59caefce8bdef327154150211000000024b8f5122000000000000000000

1 output(s) for total of 0.000666732095 xmr

stealth address amount amount idx tag
00: 52a6a6877dd0e5ac493a032f28a5e4754c15cb8c0a92a6720c5af74f492402ae 0.000666732095 1350763 of 0 -

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 dinastycoin-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": 894570, "vin": [ { "gen": { "height": 894560 } } ], "vout": [ { "amount": 666732095, "target": { "key": "52a6a6877dd0e5ac493a032f28a5e4754c15cb8c0a92a6720c5af74f492402ae" } } ], "extra": [ 1, 27, 253, 240, 96, 41, 181, 164, 187, 229, 102, 73, 254, 103, 40, 71, 41, 104, 18, 147, 25, 107, 197, 156, 174, 252, 232, 189, 239, 50, 113, 84, 21, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: