Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57349009bf59a169cd35ef0ea7a4a93dec43eb52c903d9cdc1b4d48c547466ce

Tx prefix hash: d6ea3e35759952f6f1bebbfd31638b3927bf794c24d709f860f185e862d772c4
Tx public key: 630df80a25ec49688d8a5f96e27738f06ab96801d3abc545c44a8cb344e0d334
Timestamp: 1747607772 Timestamp [UTC]: 2025-05-18 22:36:12 Age [y:d:h:m:s]: 00:361:21:35:56
Block: 1285891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248705 RingCT/type: yes/0
Extra: 01630df80a25ec49688d8a5f96e27738f06ab96801d3abc545c44a8cb344e0d3340211000000069f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 01160eec1e02fb10846d7a15a5d268cf7861868e9941fa2aa95e9718a597a73c 0.000600000000 1773356 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 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": 1285901, "vin": [ { "gen": { "height": 1285891 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01160eec1e02fb10846d7a15a5d268cf7861868e9941fa2aa95e9718a597a73c" } } ], "extra": [ 1, 99, 13, 248, 10, 37, 236, 73, 104, 141, 138, 95, 150, 226, 119, 56, 240, 106, 185, 104, 1, 211, 171, 197, 69, 196, 74, 140, 179, 68, 224, 211, 52, 2, 17, 0, 0, 0, 6, 159, 159, 230, 140, 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: