Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd95465044f2df4e832dd9b5a62621bd585b1b16bba948674a3ab1cd96e47ea7

Tx prefix hash: 724d3f6888c0213758cf69f80bde78c61506de39e6bde6ad26879a879900f0e4
Tx public key: 239c3bfe0cc4e8fa92683ed9eee579bd0396061fec1b9badaa3a2501428aa4c9
Timestamp: 1787237661 Timestamp [UTC]: 2026-08-20 14:54:21 Age [y:d:h:m:s]: 00:088:11:02:02
Block: 1617540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 62523 RingCT/type: yes/0
Extra: 01239c3bfe0cc4e8fa92683ed9eee579bd0396061fec1b9badaa3a2501428aa4c902086f4e2e879a62444a

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8dfb8422bc92f8f17518a94d5b8c9f49ff9b72c9034fbedd675cab0fba083c5a 0.000600000000 2107560 of 15 <48>

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": 1617550, "vin": [ { "gen": { "height": 1617540 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "8dfb8422bc92f8f17518a94d5b8c9f49ff9b72c9034fbedd675cab0fba083c5a", "view_tag": "48" } } } ], "extra": [ 1, 35, 156, 59, 254, 12, 196, 232, 250, 146, 104, 62, 217, 238, 229, 121, 189, 3, 150, 6, 31, 236, 27, 155, 173, 170, 58, 37, 1, 66, 138, 164, 201, 2, 8, 111, 78, 46, 135, 154, 98, 68, 74 ], "rct_signatures": { "type": 0 } }


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