Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf6d01aeea65f8b0ef1b0ebde72df4521815e095ea7ebeb3137804b3db09eb3b

Tx prefix hash: 2beba2c5e90c4f47b1e4bf52ef3ff4af6653642e2cf2b689c57051b093f359c7
Tx public key: c8f8da68c79012cf4a3047a5f21c8e29d0e14d86f54f9241b5a713f672c1a1c7
Timestamp: 1793251122 Timestamp [UTC]: 2026-10-29 05:18:42 Age [y:d:h:m:s]: 00:022:21:21:21
Block: 1665052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 18053 RingCT/type: yes/0
Extra: 01c8f8da68c79012cf4a3047a5f21c8e29d0e14d86f54f9241b5a713f672c1a1c7

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4a703910ce8cf6070320e4930f42222144dbf5f61ea873fd577692c7c869ec1f 0.000600000000 2155810 of 15 <6c>

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": 1665062, "vin": [ { "gen": { "height": 1665052 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "4a703910ce8cf6070320e4930f42222144dbf5f61ea873fd577692c7c869ec1f", "view_tag": "6c" } } } ], "extra": [ 1, 200, 248, 218, 104, 199, 144, 18, 207, 74, 48, 71, 165, 242, 28, 142, 41, 208, 225, 77, 134, 245, 79, 146, 65, 181, 167, 19, 246, 114, 193, 161, 199 ], "rct_signatures": { "type": 0 } }


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